VeraCrypt Files

Changes between 1.26.15 and 1.26.18 (20 January 2025):

  - All OSes:
     * Added support for SHA-256 x86 intrinsic to enhance the performance of PBKDF2-HMAC-SHA256.
     * Added support for AES hardware on ARM64 platforms (e.g. Windows ARM64, macOS on Apple Silicon Mx).
     * Updated translations
  - Windows:
     * Dropped support for Windows 32-bit.
     * Set Windows 10 October 2018 Update (version 1809) as the minimum supported version.
     * Reduce driver deadlock occurences under low-memory scenarios caused by re-entrant IRP completions.
     * Fixed failed EFI detection on some PCs where the BootOrder variable is not defined (proposed by @kriegste, GH #360).
     * Fixed "Access Denied" error when updating VeraCrypt using EXE setup following a Windows upgrade.
     * Fixed various issues affecting the EFI system encryption configuration editor.
     * Fixed regression in Traveler Disk creation (GH #886)
     * Replaced the deprecated CryptGenRandom with BCryptGenRandom for generating secure random bytes.
     * Use modern API to gather system entropy for random generation instead of obsolete ones.
     * Update LZMA SDK to version 24.09
     * Update libzip to version 1.11.2
  - Linux:
     * CVE-2024-54187: Added absolute paths when executing system binaries to prevent path hijacking (collaboration with SivertPL @__tfr)
     * CVE-2025-23021: Prevent mounting volumes on system directories and PATH (reported by SivertPL @__tfr)
     * Fixed an assertion issue with the wxWidgets library included in Ubuntu.
     * Improved directory-opening logic by prioritizing xdg-open and adding fallback mechanisms.
     * Ensure that volume exists before starting the mount operation.
     * Fix "Password too long" error message not expanded to include max length (GH #1456)
     * Simplify sudo session detection logic.
  - macOS:
     * CVE-2024-54187: Added absolute paths when executing system binaries to prevent path hijacking (collaboration with SivertPL @__tfr)
     * CVE-2025-23021: Prevent mounting volumes on system directories and PATH (reported by SivertPL @__tfr)
     * Disabled screen capture by default. Added the --allow-screencapture CLI switch to enable it if needed.
     * Ensure that volume exists before starting the mount operation.
     * Implement sudo session detection logic